Increasing Battery Performance for a Device That Uses Power Saving Features

ABSTRACT

Described herein are systems and methods to increase battery life of a user equipment (UE) by reducing the amount of time a UE spends in active time listening for paging messages following mobile originate (MO) or mobile terminated (MT) data transfers. A network node may receive, from a UE, a message including an identifier of the UE and a request to set the duration of an active time timer to zero. The network node may determine whether any MT traffic is available for the UE, and send a message to the UE including the duration of the active time timer or some other indicator to indicate to the UE whether or not MT data is awaiting transmission.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/045,721 filed Oct. 6, 2020, which is a U.S. National Stage ofInternational Patent Application No. PCT/EP2019/058595 filed Apr. 5,2019, which claims priority to U.S. Provisional Application No.62/654,086 filed Apr. 6, 2018, both of which are incorporated byreference herein as if reproduced in their entirety.

BACKGROUND

The Internet of Things (IoT) is a network of devices that are embeddedwith electronics, software, and sensors. IoT devices enable connectivityand communications to collect and exchange data for intelligentapplications and services. IoT devices include smartphones, tablets,consumer electronics, vehicles, motors, and sensors capable of IoTcommunications. IoT devices are referred to as cellular IoT (CIoT)devices when the IoT devices are coupled by a wireless network. In thisapplication, a CIoT device may also be referred to as User Equipment(UE), Terminal Equipment (TE), or Mobile Equipment (ME).

In order to increase the battery life of CIoT devices a feature known asPower Saving Mode (PSM) was introduced in the Third GenerationPartnership Project (3GPP) Release 12 (Rel-12). PSM is applicable tomany communications standards, such as 3GPP Global System for MobileCommunications (GSM) Enhanced Data rates for GSM Evolution (EDGE) RadioAccess Network (RAN) (GERAN), 3GPP Universal Mobile TelecommunicationSystem (UMTS) Terrestrial RAN (UTRAN), 3GPP Long Term Evolution (LTE),and other next generation (NG) communication standards, including thefifth generation (5G) System (5GS) which includes the 5G Core Network(CN) and e.g. the NG-RAN. PSM is controlled negotiated between the UEand the CN supporting the above access networks. The E-UTRAN issupported by the Evolved Packet Core (EPC) network in the Evolved PacketSystem (EPS). The NG-RAN is supported by the 5G CN in the 5GS. Whileprotocols of the access stratum are terminated in an access network, theprotocols of the non-access stratum (NAS) are terminated in the corenetwork. The NAS protocols consist of mobility management protocols andsession management protocols.

The power consumption of a UE in PSM deep sleep is similar to a UE thatis powered off, but the UE in PSM deep sleep remains registered on thenetwork. A UE in PSM deep sleep terminates listening to or avoidsmonitoring the network when entering PSM deep sleep. For example, thedevice could power off or disable receivers while remaining attached orregistered with the network. Additionally, any timers and conditionsheld during power-off, e.g. NAS-level back-off timers, may apply in thesame manner during the PSM. Furthermore, the UE is not required tosignal to attach, to establish, or to re-establish packet data network(PDN) connections when the UE needs to listen to/monitor the networke.g., to wake up, to send a message or data after leaving PSM deepsleep. In some cases, the transition from PSM deep sleep to connectedmode is triggered either by need for the UE to send mobile originated(MO) data or by the need to send, for example, a NAS mobility managementprotocol message (e.g. a location update message such as a Tracking AreaUpdate (TAU) message when using the EPS) or other NAS message.

Presently, when a UE transitions from connected mode after finishing adata transfer, the UE enters an active time where the UE listens forpaging messages prior to entering PSM deep sleep. Power consumed by theUE while listening to paging (i.e., waiting to receive mobile terminated(MT) data) is significant, especially when a UE battery is expected tolast many years. Calculations have shown, for one class of device with aspecific battery life, that power consumed when listening to pagingrepresented 12% of the total battery life. In that regard, the morefrequently the UE listens for paging, the greater the battery life whichis wasted. Within this document PSM deep sleep might also be shorted toPSM or PSM mode.

Since there is a power consumption impact associated with listening topaging following each and every session (e.g. connected mode), it wouldbe desirable for a UE that generates MO traffic only or mostly MOtraffic (MMOT) and receives delay tolerable MT traffic to not berequired to listen to paging after every session.

SUMMARY

Accordingly there are methods, a network node and a user equipment, UE,as detailed in the claims that follow.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is nowmade to the following brief description, taken in connection with theaccompanying drawings and detailed description, wherein like referencenumerals represent like parts.

FIG. 1 is a diagram of a timeline illustrating transmit and receiveperiods of a PSM enabled UE transitioning through different modes.

FIG. 2 is a block diagram of a user equipment architecture according toan embodiment of the disclosure.

FIG. 3 is a flow diagram for setting an active time timer according toan embodiment of the disclosure.

FIG. 4 illustrates an exemplary implementation of an embodiment of thedisclosure.

FIG. 5 is a flow diagram for sending a Mobility Management (MM) Acceptmessage according to an embodiment of the disclosure.

FIGS. 6A, 6B, 6C, 6D, 6E, and 6F illustrate an exemplary implementationof an embodiment of the disclosure.

FIG. 7 is a flow diagram for sending an enhanced MM Accept messageaccording to an embodiment of the disclosure.

FIGS. 8A, 8B, 8C, 8D, and 8E illustrate an exemplary implementation ofan embodiment of the disclosure.

FIG. 9 is a flow diagram for indicating MMOT Traffic Accept messageaccording to an embodiment of the disclosure.

FIGS. 10A and 10B illustrate an exemplary implementation of anembodiment of the disclosure.

FIG. 11 illustrates an exemplary implementation of an embodiment of thedisclosure.

FIGS. 12A and 12B illustrate an exemplary implementation of anembodiment of the disclosure.

FIG. 13 illustrates an exemplary implementation of an embodiment of thedisclosure.

FIGS. 14A, 14B, 14C, and 14D illustrate an exemplary implementation ofan embodiment of the disclosure.

FIG. 15 illustrates an exemplary implementation of an embodiment of thedisclosure.

FIG. 16 illustrates an exemplary implementation of an embodiment of thedisclosure.

FIG. 17 illustrates an exemplary implementation of an embodiment of thedisclosure.

FIG. 18 illustrates an exemplary implementation of an embodiment of thedisclosure.

FIGS. 19A, 19B, and 19C illustrate an exemplary implementation of anembodiment of the disclosure.

FIG. 20 is a flow diagram for MT traffic handling according to anembodiment of the disclosure.

FIGS. 21A, 21B, 21C, 21D, 21E, and 21F illustrate an exemplaryimplementation of an embodiment of the disclosure.

FIG. 22 is a diagram of extended Data Transfer sessions and TAU sessionsaccording to an embodiment of the disclosure.

FIGS. 23A, 23B, 23C, 23D, 23E, 23F, and 23G illustrate an exemplaryimplementation of an embodiment of the disclosure.

FIGS. 24A and 24B illustrate an exemplary implementation of anembodiment of the disclosure.

FIG. 25 illustrates a block diagram of a network element according to anembodiment of the disclosure.

FIG. 26 is a block diagram of a UE according to an embodiment of thedisclosure.

FIG. 27 illustrates an example processor and related components suitablefor implementing the several embodiments of the present disclosure.

DETAILED DESCRIPTION

It should be understood at the outset that although illustrativeimplementations of one or more embodiments of the present disclosure areprovided below, the disclosed systems and/or methods may be implementedusing any number of techniques, whether currently known or in existence.The disclosure should in no way be limited to the illustrativeimplementations, drawings, and techniques illustrated below, includingthe exemplary designs and implementations illustrated and describedherein, but may be modified within the scope of the appended claimsalong with their full scope of equivalents.

Described herein are systems and methods to increase battery life of aUE by reducing the amount of time a UE spends in active time listeningfor paging messages following mobile originate (MO) or mobile terminated(MT) data transfers. A network node may receive, from a UE, a messageincluding an identifier of the UE and a request to set the duration ofan active time timer to zero. The network node may determine whether anyMT traffic is available for the UE, and send a message to the UEincluding the duration of the active time timer or some other indicatorto indicate to the UE whether or not MT data is awaiting transmission.Hence, instead of always listening during active time following MOtransfers, the UE may listen during active time only when there is MTdata to be transmitted to the UE.

The UE may send a mobility management message e.g., a Detach orDe-Registration Request in 5G, Routing Area Update, Tracking Areaupdate, Location area update, etc. to the network. Upon receipt of themessage from the UE, if there is MT data pending, the network mayperform procedures as described in U.S. patent application Ser. No.14/834,216, (which is incorporated in its entirety herein by reference)using the following control messages e.g., Detach Accept orDe-registration Accept in 5G, Routing Area Update Accept, Tracking Areaupdate Accept, Location area update Accept, etc. to send pending MTdata.

As used herein, the term UE can refer to mobile devices such as mobiletelephones, personal digital assistants, handheld or laptop computers,vehicle or modem within a vehicle, Internet of Things (IoT) devices andsimilar devices that have telecommunications capabilities. Such a UEmight comprise a wireless device and its associated embedded UniversalIntegrated Circuit Card (eUICC) that includes a Subscriber IdentityModule (SIM) application, a Universal Subscriber Identity Module (USIM)application, or a Removable User Identity Module (RUIM) application ormight comprise the device itself without such a card. The term “UE” mayalso refer to devices that have similar capabilities but that are nottransportable, such as fixed line telephones, desktop computers, orset-top boxes. The term “UE” can also refer to any hardware or softwarecomponent that can terminate a Session Internet Protocol (SIP) session.

As used herein, operator initiated MT traffic includes but is notnecessarily limited to MT traffic that may be generated by the cellularoperator, e.g. an SMS message that is sent to the device to cause itsconfiguration to be changed. Furthermore, a network or network node maybe a collection or sub-collection of entities ranging from Evolved NodeB (eNB), Serving General Packet Radio Service (GPRS) Support Node(SGSN), Gateway GPRS Support Node (GGSN), Mobile Management Entity(MME), Packet Gateway (P-GW), Serving Gateway (S-GW), Access andMobility Management Function (AMF), Session Management Function (SMF),etc. It is worth noting that MME is a fourth generation function thatmay perform Mobility, Authentication, and Session Management. In 5G orNG, the MME may be split into AMF and SMF. Hence, AMF, SMF, and MME maybe interchanged herein.

A UE capable of PSM may only be reachable for MT services during a timeperiod that the UE is in connected mode and during an idle modeimmediately after the connected mode. The idle mode may include a timeperiod known as active time which follows a time period that the UE isin the connected mode. The UE may enter PSM when the active time timeperiod expires. PSM may be well suited for applications that initiate MOdata, such as a location (geographic) reporting application, a smartmeter application reporting electricity usage data, etc., where the MOdata may be sent using short message service (SMS) or via IP or non-IPdata connection. The active time time period may be represented by atimer known as an active time timer. The active time timer may also bereferred to as T3324 specified in 3GPP TS 24.008. The UE may request anactive time timer value during Attach (i.e., when the UE performs aninitial registration to the network) or during TAU to a network entity,such as an MME or SGSN. The MME/SGSN may determine whether the UE mayuse PSM and may inform the UE of the active time timer value that shouldbe used if the UE is allowed to use PSM. The MME/SGSN may take the UErequested active time timer value and any local MME/SGSN configurationinto account for determining the active time timer value that may beallocated to the UE. Based on 3GPP Rel-12, a minimum recommended lengthfor the active time timer is a time allowing for a ‘msg waitingindication’ in the MME/SGSN to trigger an SMS Center (SMSC) via a homesubscriber server (HSS) to deliver an SMS to the MME/SGSN, e.g. twodiscontinuous reception (DRX) cycles plus 10 seconds. DRX is anothermethod used in mobile communications to conserve battery life of the UE.For DRX, the UE and the network may negotiate periods in which the UEwill listen to control channels, during other DRX times where the UE isnot listening to control channels, the UE may turn its receiver off andenter a low power state.

FIG. 1 is a diagram of a timeline of a PSM enabled UE transitioningthrough different modes. As shown in FIG. 1 , a UE may change operationmode over a period of time, e.g. a first time period 110 to a secondtime period 120 to a third time period 130. The first time period 110may be triggered by an MO data transfer event (e.g. to transmit an SMSmessage) or by a TAU message transfer event e.g. periodic TAU. The firsttime period includes a connected time period 112 and an active timetimer time period 114. The active time timer time period 114 may bereceived from the MME/SGSN at Attach or previous TAU procedures. Duringthe active time timer time period 114, the UE may be in an idle stateand listen for paging messages. The second time period 120 may startafter expiration of the active time timer time period 114. During thesecond time period 120 the UE may be in PSM deep sleep. A length of thesecond time period may be determined according to a timer known asperiodic TAU timer 122. The periodic TAU timer may also be referred toas T3412 as specified in 3GPP TS 24.008. The UE may be configured toexit PSM deep sleep at the end of the periodic TAU timer time period 122to the third time period 130. The third time period 130 may include aconnected mode 132 and a active time timer time period 134 and may be indevice reachable state for the MT traffic, transmit MO traffic, etc.

The periodic TAU may be used to inform the network that the UE stillneeds service and that the UE's contexts within the network are to bemaintained. The periodic TAU timer of the UE may start after the lastTAU or data transfer event and the periodic TAU message may be sent whenthe periodic TAU timer expires. Both the periodic TAU timer and theactive time timer values may be set by the MME/SGSN. In someembodiments, a UE capable of PSM may request the periodic TAU timer andthe active time timer values according to UE requirements. Hence, for anapplication generating an MO message with a known periodicity (e.g. anasset tracking application which sends location reports every 24 hours),the UE may request a periodic TAU timer value to be larger than thistime period (e.g. 25 hours). Noting that the periodic TAU timer T3412 isreset after completion of every data session or TAU session. This willsave power in the UE by avoiding unnecessary TAU messaging. A UE canrequest a new value for the periodic TAU timer during Attach or TAUprocedures. As specified in 3GPP TS 24.008, a value range for the activetime timer may be 0 seconds up to maximum of 3.1 hours and a value rangefor periodic TAU timer may be 0 to 413 days. Other values of active timetimer and periodic TAU timer may be used as appropriate.

PSM may be used by UEs using Packet Switched (PS) domain, SMS andInternet Protocol (IP) Multimedia Subsystem (IMS). In LTE/Evolved UTRAN(E-UTRAN), SMS can be sent and received over the radio control channelor they can be sent using IMS messaging. Due to the fact that the SMS isa store and forward procedure, indications are specified in the networkthat indicate if a message cannot be delivered because the UE could notbe reached (i.e., the UE is in the PSM deep sleep), which then enablesthe delivery to be reattempted. Additionally, the indications mayinclude a Message Waiting Indication (MWI) that is stored in the MobileSwitching Center (MSC)/Visitor Location Register (VLR), SGSN, MME and/oran indication that is stored in the Home Location Register (HLR)/HSSindicating which SMSC should be notified when the UE becomes availableagain.

In an embodiment, an active time timer may start at the end of theconnected mode, for example following transition from connected to idle.For applications that generate MO traffic, one instance of listening topaging is when a cellular operator wishes to contact the UE to enablethe cellular operator to deliver a message to the UE (e.g. SMS message)for a configuration update. Certain applications may not need to receiveMT traffic and the UE may request from the MME to set the active timetimer value to zero. If the MME has been configured to disregard the UErequested value in all or some circumstances and sets a pre-configuredvalue from the MME instead, then the UE will be required to monitor thenetwork for an operator defined and potentially non-zero active timetimer period. Furthermore, the cellular operator might choose todisallow the requested active time timer value of zero if the cellularoperator has a requirement to send MT configuration messages to the UE.

FIG. 2 is a block diagram of a UE architecture 200 for attention (AT)commands according to an embodiment of the disclosure. The UEarchitecture 200 may include a mobile termination (MT) 220 thatcommunicates with terminal adaptor (TA) 212. In an embodiment, TA 212may communicate with terminal equipment (TE) 211 using AT commands(designated as “AT cmds” in FIG. 2 ).

AT commands may enable upper layers of a TE (e.g. application layer) towrite data, read data, or request execution of a procedure by lowerlayers of the TE (e.g. modem chipset). The lower layer may providefinal, and/or intermediate responses to AT commands. The lower layersmay provide unsolicited codes as responses, e.g. incoming on callannouncement (i.e., RING) or an equivalent when an incoming call isdetected. The TE may register for receiving certain unsolicitedcodes/responses by means of AT commands.

FIG. 3 is a flow diagram 300 for setting an active time timer T3324according to an embodiment of the disclosure. The flow diagram 300 maybe implemented between a UE 310 and a network node 320.

At step 301, the UE 310 may send a first message including a useridentity to the network node 320. The user identity corresponds to theUE 310. The first message may include an Attach request, a Routing AreaUpdate (RAU) request, a TAU request and/or a Location Area Update (LAU)request. Other types of requests may be included in the first message asnecessary. Further, the first message may include an indication that theUE 310 requests use of PSM and a request to set the active time timervalue to be zero.

At step 303, the network node 320 may determine whether an MWIindication corresponding to the user identity of the UE 310 is set. Inan embodiment, the MWI indication has been expanded to be a more genericterm that implies there is data waiting for the UE, and the data may beSMS or MT Packet Data Unit (PDU). In some embodiments, the MWIindication has also been expanded to include a sub-type of data e.g.operator, application, user etc. If and when a UE receives this sub-typeit can make a more informed decision if the active time timer should berun or not.

At step 304 a, the network node 320 sets the active time timer value tozero and includes the active time timer value in a second message if theMWI indication corresponding to the user identity is not set.

At step 304 b, the network node 320 disregards the request for theactive time timer value to be set to zero if the MWI indicationcorresponding to the user identity is set. In this situation, thenetwork node 320 may set the active time timer value to a predeterminedvalue greater than zero.

The second message may be an Attach accept, an RAU accept, a TAU acceptand/or a LAU accept or S1-AP message (or 5G equivalent). In someembodiments, other data may be included in the second message asnecessary.

At step 305, the network node 320 may send the second message to the UE310.

FIG. 4 illustrates an exemplary implementation 400 of an embodiment ofthe disclosure. The implementation 400 corresponds to an implementationspecified by 3GPP TS 23.682, with changes proposed herein denoted byunderlined text. The implementation is a possible solution out of manyto implement the embodiments described herein.

FIG. 5 is a flow diagram 500 for sending a Mobility Management (MM)Accept message according to an embodiment of the disclosure. The flowdiagram 500 may be implemented between a UE 510 and a network node 520.

At step 501, the UE 510 may send a first message optionally includingeither or both a user identity and active time timer to the network node520. The user identity corresponds to the UE 510. In an embodiment, thefirst message may include a Service Request, Attach request, an RAUrequest, a TAU request, and/or a LAU request. Other requests may beincluded in the first message as necessary.

At step 502, the network node 520 may determine if there is any data(i.e., downlink data such as SMS or MT PDU) waiting to be delivered tothe UE 510. If data is waiting the MWI indication is set to True and ifdata is not waiting the MWI indication is set to False.

At step 503, the network node 520 may include an indication e.g. MWIindication) in a second message corresponding to a determining result instep 502. For example, the MWI indication may be set to “TRUE” whenthere is data waiting (e.g. SMS, MT PDU etc) to be delivered and the MWIindication may be set to “FALSE” when there is no data waiting to bedelivered. In an embodiment, the second message may include but notlimited to an Attach accept, an RAU accept, a TAU accept, and/or a LAUaccept, or S1-AP message (or 5G equivalent) etc. In some embodiments,other data may be included in the second message as necessary.

At step 504, the network node 520 may send the second message to the UE510.

At step 505, the UE 510 may send MO data (i.e., SMS, PDU) or MO message(e.g. periodic TAU message, etc.) to the network node 520 afterreceiving the second message.

At step 506, the UE 510 may determine not to run the active time timerand transition to PSM deep sleep when the MWI indication is set to“FALSE” and run the active time timer and transition to PSM deep sleepwhen active time timer expires when the MWI indication is set to “TRUE”in the optional indication.

In an optional step 507, the UE 510 may send a Mobility Management (MM)message including an indication (e.g. PSM indication) indicating thatthe UE 510 is entering into PSM.

In an optional step 508, the network node 520 may set an indication thatthe UE 510 has entered PSM deep sleep after receiving the MM Requestmessage including the PSM indication from the UE 510. Furthermore,context data (i.e., network registration information of UE 510) may besaved in the network node 520. While the UE 510 is in PSM deep sleep, ifthe network node 520 receives any Mobile Terminated (MT) traffic for theUE 510 an indication may be returned to the sender indicating that theUE 510 is unreachable.

In optional step 509, the UE 510 transitions to idle state and mayrelease the bearer.

In an embodiment, the network node 520 may use the following process todetermine whether there is any downlink data (e.g. SMS or MT PDU)pending. In an embodiment, the network node 520 may set an SMSC addressor an origination address in a short message to be used to distinguishthe type of traffic (see Table 1). Distinguishing the type of trafficmay require configuration of information in an entity that performs thedetermining, for example the network node 520. A set of parameters thatcan be used to distinguish the type of traffic received is shown inTable 1 below. Information could be stored in the following (but notlimited to): network node 520, UE 510, a UICC application, a TE, etc.

TABLE 1 Information element Address(value[s] to analyse in the MTreceivedinthe Sub-type of traffic (service traffic proceeding column)type) SMSC address A (1^(st) address) Operator (1 st service type) B(2^(nd) address) Application (2^(nd) service type) A (1st applicationtype) C User (3^(rd) service type) MO short message D Operator address EApplication F User Origination IP address G Operator H Application A Iuser Origination port J Operator K Application L User Transport protocolM Operator Destination IP address N User Destination port O Application

The address could be a single entry, multiple entries, or a range ofaddresses. Letters are used in the Table 1 for illustrative purposes torepresent the address(s).

In an embodiment, the network node 520 may receive the MT data (e.g. ashort message) and may be unable to deliver the MT data to the UE 510(e.g. UE 510 is the PSM). The network node 520 may analyze, for example,the SMSC address in the MT data and match the SMSC address to an addressstored in memory of the network node 520 (e.g. Address A) (see table 1).The network node 520 may determine that the MT data is operator shortmessage traffic based on the matching result.

Similar operations can be performed for other types of traffic e.g IPtraffic. Table 1 illustrates a number of information elements (IE) thatcould be analyzed (1st column) and then matched against possible entriesthat could appear in that IE (column 2). If a match is found then asub-type is determined (column 3). This sub-type maybe then communicatedto the UE e.g. in step 504 of FIG. 5 . The UE then use this sub-type, ifreceived, to determine if active time timer T3324 should be run or note.g. Table 2.

In an embodiment, the following Table 2 may be stored in the UE 510 and“Run active time timer” or “Not run active time timer” action may beperformed based on the MWI indication status (e.g., “TRUE” or “FALSE”).The action to perform may either run active time timer (e.g. an activetime timer value greater than zero was received) or not run active timetimer. For example, if an MWI indication is set for a certain data type,e.g. Operator MT SMS, the action to perform may be ‘run active timetimer.’ In another example, the UE is informed that “user” SMS iswaiting, however the UE never expects to receive “user” SMS so ignoresactive time timer and transitions to PSM deep sleep. Such an SMS couldbe seen as an attack to run the battery down as the device would have toconsume power waiting for the SMS to be delivered. As shown in Table 2,the first column represents types of traffic e.g. Operator MT SMS,Operator MT data, etc., and the second column represent an action toperform e.g. Run active time timer, Not run active time timer, etc.

TABLE 2 Data type waiting Action to perform Operator MT SMS Run activetime timer Operator MT data Not run active time timer 1^(st) applicationNot run active time timer (Application a) MT data 2^(nd) application Runactive time timer (Application b) MT SMS User data Run active time timerUser SMS Not run active time timer MT data Run active time timer MT SMSRun active time timer MT PDU Not run active time timer

FIGS. 6A, 6B, 6C, 6D, 6E, and 6F illustrate an exemplary implementation600 of an embodiment of the disclosure. The implementation 600corresponds to an implementation specified by 3GPP TS 24.301, withchanges proposed herein denoted by underlined text. The implementationis a possible solution out of many to implement the embodimentsdescribed herein.

FIG. 7 is a flow diagram 700 for sending an enhanced MM Accept messageaccording to an embodiment of the disclosure. The flow diagram 700 maybe implemented between a UE 710 and the network node 720.

At step 701, the UE 710 may send a first message optionally including auser identity to the network node 720. The user identity corresponds tothe UE 710. In an embodiment, the first message may include a ServiceRequest, Attach request, an RAU request, a TAU request, REGISTER and/ora LAU request. Other requests may be included in the first message asnecessary.

At step 702, the network node 720 may determine if there is any data(e.g. downlink data such as SMS or MT PDU) waiting to be delivered tothe UE 710.

At step 703, the network node 720 inserts an optional indication into asecond message when there is data waiting for the UE 710. In anembodiment, the second message includes but not limited to an Attachaccept, an RAU accept, a TAU accept, REGISTER ACCEPT and/or a LAUaccept, or S1-AP message (or 5G equivalent). In some embodiments, otherdata may be included in the second message as necessary. In anembodiment, the optional indication indicates “MMOT traffic supported”has been set or “MMOT traffic supported” has not been set. The “MMOTtraffic supported” indicates that the MT data may be stored in thenetwork node 720 for a pre-determined time or in another network node inthe network or MMOT means that the device generates mobile originatedtraffic and does not want to receive MT traffic, however it is preparedto receive MT traffic that has originated from the operator e.g. SMSOTA. Elsewhere in the document there are descriptions that describe howtraffic can be characterized as being from the operator. MMOT may alsobe referred to herein as Delaytolerable Traffic or Delaytolerable MTTraffic.

At step 704, the network node 720 may insert a timer X1 into the secondmessage and may insert active time timer. The network node 720 may setto start Timer X1 either upon sending this message, upon expiry ofactive time timer or upon completion of the mobility managementprocedure. In one implementation, when Timer X1 is started the networknode 720 may assume that the UE 710 may use the active time timer thathas also been inserted into the same message for the period of time ofTimer X1. The network node 720 may also assume not to expect the receiptof an active time timer value from the UE 710 for the period of TimerX1. Alternatively, Timer X1 may include a value indicating the number ofmobility management messages that the UE may send not containing anactive time timer value, however the UE 710 may still use the sameactive time timer value as was included with the Timer X1 value. Yetanother implementation, Timer X1 indicates to the UE 710 how long it canignore active time timer if MMOT is true.

At step 705, the network node 720 may send the second message to the UE710.

At step 706, the UE 710 may send MO data to the network after receivingthe second message.

At step 707, the UE 710 may determine, based on the optional indicationstatus, to ignore the active time timer and enter PSM deep sleep or toexecute active time timer and upon expiration of active time timerperform PSM deep sleep. The determination to ignore the active timetimer occurs when the optional indication indicates the MMOT traffic issupported and the determination to execute the active time timer occurswhen the optional indication indicates the MMOT traffic is notsupported. If the UE 710 does ignore active time timer, sometime laterit needs to decide to execute active time timer so that it may receivethe MT traffic.

At step 708, the UE 710 may repeat sending the first message when theperiodic TAU timer expires or when the Timer X1 received from the secondmessage expires. In an embodiment, the timer X1 may be stored in memoryof the UE 710 or on the UICC application (and subsequently read into UE710 memory). In this way, the UE 710 may de-couple the times at whichthe UE 710 listens for MT traffic from the times at which the MO datatransfers or TAU messages are sent. Hence, rather than listen for MTtraffic after every MO session, the UE 710 may listen for MT traffic ata less frequent rate that is dictated by the needed acceptable delay insending the MT traffic. In an embodiment, the Timer X1 may also indicateto the UE that for the period of Timer X1 the UE does not need toinclude the active time timer (e.g. timer UE needs to monitor pagingchannel) in messages to the network (e.g. Service Request, REGISTER,Location Update, Tracking Area Update, etc.) or Timer X1 may be a valuethat indicates the number of messages that may be sent to the networkthat do not include the active time timer. In both of these embodiments,the active time timer value used by the UE is the same value that wasreceived in the message that contained Timer X1. This means that the UEsends and receives less information elements, bytes, to and from thenetwork consuming less power.

FIGS. 8A, 8B, 8C, 8D, and 8E illustrate an exemplary implementation 800of an embodiment of the disclosure. The implementation 800 correspondsto an implementation specified by 3GPP TS 24.301, with changes proposedherein denoted by underlined text. The implementation is a possiblesolution out of many to implement the embodiments described herein.

FIG. 9 is a flow diagram 900 for indicating MMOT Traffic Accept messageaccording to an embodiment of the disclosure. The flow diagram 900 maybe implemented between a UE 910 and a network node 920.

At step 901, the UE 910 may send a first message optionally including auser identity to the network node 920. The user identity corresponds tothe UE 910. In an embodiment, the first message may include but notlimited to a Service Request, Attach request, an RAU request, REGISTER,a TAU request and/or a LAU request. Other types of requests may beincluded in the first message as necessary. Furthermore, the UE 910 mayinclude an optional indication indicating that the UE 910 supports theMMOT.

At step 902, the network node 920 may determine if there is any data(i.e., downlink data such as SMS or MT PDU) waiting to be delivered tothe UE 910. In this embodiment, if there is any MMOT data to be sent toUE 910, may be implemented using the steps denoted in the description ofTable 1.

At step 903, an active time timer value may be determined according toTable 3 and included in a second message. Table 3 is an extension ofTable 1, and in addition to the columns shown in Table 1, Table 3includes a fourth column indicating possible active time timer valuesaccording to the sub-type of determined MMOT data.

TABLE 3 Active time timer Information element to Sub-type of trafficvalue (a timer analyze Address (service type) value) SMSC address(1^(st) A Operator(1^(st) X (1^(st) value) information element) servicetype) B Application A (2^(nd) Y (2^(nd) value) service type) c User(3^(rd) service Z (3^(rd) value) type) Mobile Originated Short DOperator K Message address (2^(nd) E Application L information element)F User Y Origination IP address G Operator XX (3^(rd) informationelement) H Application A YY I user XY Origination port (4^(th) JOperator XC information element) K Application CC L User DD Transportprotocol (5^(th) M Operator SS information element) Destination IPaddress N User AA (6^(th) information element) Destination port (7^(th)O Application ZZ information element)

Certain addresses and parts are shown in Table 3. In some embodiments,other parts, addresses, and/or data may be used in determining thesubtypes of traffic and/or the active time timer. One will appreciatethat the letters that appear in the 2^(nd) and 4^(th) column are purelyfor illustrative purposes and are used to demonstrate that differentdata maybe contained however the data maybe the same. The letters incolumn 2 represent data, and the data maybe textual, numeric, andalphanumeric. The data maybe a single, group of, range of entries or anycombination thereof.

In an embodiment, when there is more than one sub-type of traffic, thenetwork node 920 may set the highest possible active time timer value asthe active time timer value for the UE 910 from Table 3.

At step 904, the network node 920 may send the second message to the UE910.

At step 905, the UE 910 may send MO data (e.g. SMS, IP PDU, non-IP PDUor periodic TAU message) to the network node 920 after receiving thesecond message.

At step 906, the UE 910 may start a time using the active time timervalue received from the network node 920.

At step 907, the network node 920 may send MT data (e.g. SMS or MT PDU)to the UE 910 after the UE starts active time timer. The MT data may betransmitting according to the procedures of U.S. patent application Ser.No. 14/834,216 or in other mobility management messages, e.g., AttachAccept, RAU Accept, TRAU Accept, LAU Accept, etc. and the 5G equivalentof messages that acknowledge REGISTRATION, periodic updates and updatesdue to moving across mobility management areas, e.g., Downlink NAStransport.

At step 908, the UE 910 may PSM deep sleep after the set active timetimer expires.

FIGS. 10A and 10B illustrate an exemplary implementation 1000 of anembodiment of the disclosure. The implementation 100 corresponds to animplementation specified by 3GPP TS 23.682, with changes proposed hereindenoted by underlined text. The implementation is a possible solutionout of many to implement the embodiments described herein.

FIG. 11 illustrates an exemplary implementation 1100 of an embodiment ofthe disclosure. The implementation 1100 corresponds to an implementationspecified by 3GPP TS 23.401, with changes proposed herein denoted byunderlined text. The implementation is a possible solution out of manyto implement the embodiments described herein.

FIGS. 12A and 12B illustrate an exemplary implementation 1200 of anembodiment of the disclosure. The implementation 1200 corresponds to animplementation specified by 3GPP TS 23.301, with changes proposed hereindenoted by underlined text. The implementation is a possible solutionout of many to implement the embodiments described herein.

FIG. 13 illustrates an exemplary implementation 1300 of an embodiment ofthe disclosure. The implementation 1300 corresponds to an implementationspecified by 3GPP TS 24.008, with changes proposed herein denoted byunderlined text. The implementation is a possible solution out of manyto implement the embodiments described herein.

In an embodiment, the active time timer T3324 may be triggered/startedwith a first TAU message or data packet transfer from the UE to thenetwork node. The active time timer value may be agreed at a previouscommunication with the network node or configured when the UE registerswith the network. Furthermore, the following two cases will occur inthis situation. When the UE sends an uplink packet (e.g. MO data orperiodic TAU message, etc.), the active time timer may be started and ifthe active time timer expires before the UE sends all of the uplinkpackets, the UE may enter PSM deep sleep when there are no more datapackets to send. If active time timer does not expire before the UEsends all of the uplink packets, the UE may transition from connectedmode to idle mode and PSM deep sleep when the active time timer expires.

In an embodiment, with respect to FIGS. 14A-18 , a control planeoptimization data transfer procedure may be modified to further optimizethe idle and PSM deep sleep transition procedure. Control planeoptimization may include that data is carried in a NAS message.Therefore, it may be possible to re-use NAS security, avoid using accessstratum security configurations and further avoid use of configurationsassociated with establishing a user plane connection. These actions mayresult in power consumption improvement. In addition, a ReleaseAssistance Indicator (RAI) may be included by the UE to inform thenetwork node whether the session comprises just one uplink packet, anuplink packet followed by a downlink packet, or some other combinationof uplink and/or downlink packets. This information may be used by thenetwork node to determine the earliest possible time to release a RadioResource Control (RRC) connection. In this embodiment, the control planeoptimization data transfer procedure may be modified such that when thenetwork node releases an S1 connection, the network node may provide anindication known as PSM State Transition Indicator within an informationelement e.g NAS container, to an access node, such as an eNB. One of themeanings of the PSM state transition indicator indicates to thereceiving entity what state the receiving entity may transition to uponreceiving an RRC message e.g. RRC connection release. The access nodemay then pass the network node provided indication onto the UE in theRRC connection release message to indicate to the UE to remain in idlestate for an assigned active time timer or transition direct to PSM deepsleep. The network node may determine to set the PSM State TransitionIndicator based on UE's previous indications of “MO originated sessionsonly” and uplink/downlink packets to be received/delivered. Note thatwithin this application S1 procedures are related to 4G, however thefunctionality can be equally applied to 5G system that uses N2procedures.

FIGS. 14A, 14B, 14C, and 14D illustrate an exemplary implementation 1400of an embodiment of the disclosure. The implementation 1400 correspondsto an implementation specified by 3GPP TS 23.401, with changes proposedherein denoted by underlined text. The implementation is a possiblesolution out of many to implement the embodiments described herein.

FIG. 15 illustrates an exemplary implementation 1500 of an embodiment ofthe disclosure. The implementation 1500 corresponds to an implementationspecified by 3GPP TS 36.413, with changes proposed herein denoted byunderlined text. The implementation is a possible solution out of manyto implement the embodiments described herein.

FIG. 16 illustrates an exemplary implementation 1600 of an embodiment ofthe disclosure. The implementation 1600 corresponds to an implementationspecified by 3GPP TS 24.301, with changes proposed herein denoted byunderlined text. The implementation is a possible solution out of manyto implement the embodiments described herein.

In another embodiment, resetting the periodic TAU timer configured inthe UE may be performed after an initial Attach and after completion ofa TAU procedure (or RAU procedure). Hence, the periodic TAU timer maynot be reset after completion of each data transfer. Each time the UEperforms the periodic TAU procedure, the UE may remain in an idle statefor a time indicated in the active time timer, during which the UE maylisten for paging and MT messages from the operator. When the UEgenerates only MO data, the UE may directly transition from connected toPSM deep sleep following RRC connection release.

In this embodiment, a UE may receive MT traffic generated by theoperator with a given configurable maximum latency that is ultimatelyset by the operator (i.e. that is determined by the periodic TAU timer).In addition, the UE may avoid unnecessarily listening for MT traffic onother occasions when sending MO traffic, and avoids the associated powerconsumption costs.

FIG. 17 illustrates an exemplary implementation 1700 of an embodiment ofthe disclosure. The implementation 1700 corresponds to an implementationspecified by 3GPP TS 23.682, with changes proposed herein denoted byunderlined text. The implementation is a possible solution out of manyto implement the embodiments described herein.

FIG. 18 illustrates an exemplary implementation 1800 of an embodiment ofthe disclosure. The implementation 1800 corresponds to an implementationspecified by 3GPP TS 24.301, with changes proposed herein denoted byunderlined text. The implementation is a possible solution out of manyto implement the embodiments described herein.

In another embodiment, when a UE indicate to the network during Attach,TAU procedure, RAU procedure, etc. that the UE or its application onlyneeds MO sessions, the network node may identify that the only MTtraffic transmitting to the UE is MT traffic the operator/network maygenerate. If the operator/network has none of the MT traffic pending, itmay be possible to expedite the return of the UE to PSM, i.e., withouttriggering active time timer. However, if the operator/network generatedMT traffic is pending, then the network node may initiate one or anycombination of foregoing embodiments described in this disclosure.

In some embodiments, the UE indicating to the network node a specificrequirement, such as, only needing MO sessions or that MMOT traffic willbe supported, etc. may be done using AT commands. For an example a “set”AT command may be used to inform the modem to inform the network of theUE's configuration to only expect to participate in MO sessions, unlessthe operator needs to originate a mobile terminated session.

An existing “set” AT command may be modified or a different “set” ATcommand may be created. FIGS. 19A, 19B, and 19C illustrate an exemplaryimplementation 1900 of an embodiment of the disclosure. Changes proposedherein are denoted by underlined text. The implementation is a possiblesolution out of many to implement the embodiments described herein. Adifferent “set” AT command may be created providing the informationneeded to inform the network of the UE's preference or configuration.

In an embodiment, one or more of the foregoing embodiments may becombined to enhance battery life of a UE. In this embodiment, withrespect to the FIG. 20 , one such possible combination of embodimentsincluding optional enhancements is discussed, and could equally beapplicable to the other possible combinations of different embodimentsdescribed herein. As shown in FIG. 20 , a flow diagram 2000 may beimplemented between the UE 2010 and a network node 2020. A TA 2014 and aTE 2012 are integrated into the UE 2010. The network node 2020 mayinclude a network node such as MME or SGSN.

Step 2001: The network node 2020 may receive MT data. The received MTdata may include an SMS, an MT PDU, or a control message indicating thatthe MT data is waiting. The message may contain the type/subtype of MTdata.

Step 2002: The network node 2020 may attempt to contact the UE 2010 andmay be unsuccessful. The UE 2010 may be in PSM deep sleep and therefore,the UE 2010 may not be reachable by the network node 2020.

Step 2003: The network node 2020 may store an indication indicating thatthe MT data is waiting. The indication may also include type of MT datasuch as, SMS, MT PDU, etc. and/or sub-type of MT data such as,Application, Operator Message, or User message. Ways of determining thesub-type of data have been explained elsewhere within this application.

Step 2004: The TE 2012 may use AT commands (as discussed previously),using the TA 2014 to include optional indicators, such as “only needingMO sessions,” “MMOT traffic will be supported,” etc. in the UE 2010messages sent to the network nodes.

Step 2005: The UE 2010 may send a first message to the network node2020. The first message optionally may include a user identitycorresponding to the UE 2010. In an embodiment, the first message mayinclude a Service Request, Attach request, an RAU request, a TAUrequest, REGISTER and/or a LAU request. Other types of requests may beincluded in the first message as necessary.

Step 2006: The network node 2020 may determine if there is any data(i.e., downlink data such as SMS or MT PDU) waiting to be delivered tothe UE 2010 and the network node 2020 may send a second messageincluding an indication indicating data availability to the UE 2010.

Step 2007: The TA 2014 may send to the TE 2012 data that was received instep 2006. Upon receipt of the data from the TA 2014, the TE 2012 maydetermine if the UE should transition to PSM deep sleep or honor theactive time timer T3324.

Step 2008: The UE 2010 may send to the network node 2020 a third messageindicating the Detachment of the UE 2010 from the network at theexpiration of the active time timer T3324 or the UE is entering PSM deepsleep mode.

FIGS. 21A, 21B, 21C, 21D, 21E, and 21F illustrate an exemplaryimplementation 2100 of an embodiment of the disclosure. Theimplementation 2100 corresponds to an implementation specified by 3GPPTS 24.301, with changes proposed herein denoted by underlined text. Theimplementation is a possible solution out of many to implement theembodiments described herein.

FIG. 22 is a diagram of extended Data Transfer sessions and TAU sessionsaccording to an embodiment of the disclosure. The Data Transfer sessionsand the TAU sessions are extended as needed according to whether a“Connection Maintenance Indication” is set at a network node. Inaddition Timer values as specified elsewhere in this application maybealso sent.

In an embodiment, the operator may need to be able to configure UEswithin a required maximum latency (designated as TOpCfg). The operatormay be aware that the UEs will access the network at least everyperiodic TAU timer. In this embodiment, the periodic TAU timer may bedesignated as T_(TAU) seconds. The operator may set T_(TAU) to be lessthan or equal to T_(OpCfg). If the operator requires that all UEs beupdated within 24 hours (i.e., T_(OpCfg)=24 hours), the operator may setT_(TAU) to be 24 hours or less. Hence, the operator may transferconfiguration data to the UEs when the UEs access the network accordingto newly set T_(TAU). The RRC connection may be held longer for purposesof operator generated MT traffic delivery, either as part of a “TAUsession” or as a part of a “Data Transfer session.”

FIG. 22 includes illustrative examples of three UEs (designated as UE#1, E #2 and UE #3) and three traces 2201, 2202 and 2203. As shown inFIG. 22 , UE #1 may follow the trace 2201 including, from left to right,a TAU session 2209 and subsequent series of data transfer (i.e., MOdata) sessions 2206, the UE #2 may follow the trace 2202 including, fromleft to right, a series of TAU sessions 2210 and 2207, and the UE #3 mayfollow the trace 2203 including, from left to right, a data transfersession 2211 and subsequent series of TAU sessions 2208. The operatormay start the device configuration roll out at time indication 2204 andfinishes the device configuration roll out at time indication 2205, withduration between time 2204 and time 2205 being T_(OpCfg).

In first trace 2201, the first data transfer event 2206 occurs afterindication 2204 and before indication 2205. Therefore, operatorconfiguration for UE #1 may be triggered during the first data transfersession 2206 and the session 2206 is extended to facilitate operatorconfiguration data delivery. Similarly, as indicated in FIG. 22 , thefirst TAU sessions 2207 and 2208 of UE #2 and UE #3 that occur withinthe T_(OpCfg) window may be extended.

In an embodiment, controlling a duration of a data transfer session mayinclude two options, at User Plane Optimization and at Control PlaneOptimization. In an embodiment, the regular User Plane and User PlaneOptimization may include the following steps.

At step 1, a UE may request from a network node an active time timervalue to be set to zero by sending a first message.

At step 2, the network node may grant the active time timer value set tozero and may send a second message including the active time timer tothe UE.

At step 3a, for the regular User Plane connectivity, the UE may send aService Request to the network node.

At step 3b, for the User Plane Optimization, the UE may send RRCConnection Resume to an access node (such as eNB), which causes theaccess node to send a message e,g, S1-AP UE CONTEXT RESUME REQUEST tothe network node.

At step 4, the network node may detect whether any or all of thefollowing S1 parameters: a Connection Maintenance Indication is set, ifany optional timers need to be included, the type of MT data waiting.The access node is informed by e.g. extending an existing field or a newfield in the message e.g. S1-AP INITIAL CONTEXT SETUP REQUEST or S1-APUE CONTEXT RESUME (i.e. for User Plane Optimization) (equivalent 5Gmessages maybe also extended) whether the Connection MaintenanceIndication is set and hence whether or not the access node needs to holdthe RRC connection for longer time period.

At step 5, the UE may send an Access Stratum RAI to the access node atthe end of the data transfer session.

If the access node was informed during the S1-AP INITIAL CONTEXT SETUPREQUEST or S1-AP UE CONTEXT RESUME that there is no MT data waiting(e.g. operator configuration data) then the access node may release theRRC connection.

If the access node was informed during the S1-AP INITIAL CONTEXT SETUPREQUEST or S1-AP UE CONTEXT RESUME that there is MT data waiting, thenthe access node may hold the RRC connection for a pre-configured timeperiod despite having received the RAI from the UE. Or it may hold theconnection for period of timer that has been identified by the includedtimer or if the subtype of MT data was included hold the connection forthe period of time for that sub-type of MT data.

The pre-configured time period may be defined either by the access nodeor the network node (e.g. MME, SGSN, AMF, SMF etc.) that sent the S1-APmessages. When the time period is received from the network node, thetimer could be in a new or existing IE. The timer value maybe set perother embodiments in this application e.g table 3.

FIGS. 23A, 23B, 23C, 23D, 23E, 23F, and 23G illustrate an exemplaryimplementation 2300 of an embodiment of the disclosure. Theimplementation 2300 corresponds to an implementation specified by 3GPPTS 36.413, with changes proposed herein denoted by underlined text. Theimplementation is a possible solution out of many to implement theembodiments described herein.

In an embodiment, controlling the duration of data transfer session inControl Plane Optimization may include the following steps.

At step 1, the UE may request the network node to set the active timetimer value to be zero.

At step 2, the network node may grant the requested active time timerwith value set to zero. In this way there may be no longer an idle modeperiod where the UE is required to listen for paging.

At step 3, when a MO Data over NAS message arrives at the network node,the network node may detect whether a Connection Maintenance Indicationis set.

At step 4a, if the Connection Maintenance Indication is set, then thenetwork node may delay releasing the S1 connection until the pending MTtraffic is delivered.

At step 4b, if the Connection Maintenance Indication is not set, thenetwork node may trigger releasing the S1 and RRC connections as soon asthe MO data transfer session is completed and according to the UEprovided NAS Release Assistance Indicator.

In an embodiment, controlling a duration of TAU session may include thefollowing steps.

At step 1, the network node may inform the access node when theconnection needs to be held (e.g., when the Connection MaintenanceIndication is set).

At step 2, when receiving a TAU REQUEST message, the network node maydetect whether the Connection Maintenance Indication is set.

At step 3a, the network node may set a new field in the S1-AP DOWNLINKNAS TRANSPORT message (e.g. NAS downlink container message) carrying theTAU ACCEPT to inform the access node that the RRC signaling connectionshall be kept for a longer period if the Connection MaintenanceIndication is set.

At step 3b, the network node may set the new field to indicate that theaccess node should release the RRC connection when the TAU communicationis complete if Connection Maintenance Indication is not set.

Similar to the case of TAU messaging, in an Attach message a new fieldindicating “hold the RRC connection” may be included in S1-AP INITIAL UECONTEXT SETUP REQUEST, where the Connection Maintenance Indication maybe an indication indicating that the MT traffic is available for the UE.Furthermore, even though the foregoing embodiments use 4G terms, thefunctionality is equally applicable to 5G system, where by S1-AP INITIALCONTEXT (RESUME, REQUEST) may be replaced with eitherNsmf_PDUSession_ReleaseSMContext response, N2 SM Resource Releaserequest or N1 SM container.

FIGS. 24A and 24B illustrate an exemplary implementation 2400 of anembodiment of the disclosure. The implementation 2400 corresponds to animplementation specified by 3GPP TS 36.413, with changes proposed hereindenoted by underlined text. The implementation is a possible solutionout of many to implement the embodiments described herein.

The various methods or operations described herein may be implemented ina 3GPP 4G network and any equivalent components in a 3GPP 5G network.Further, the embodiments described herein may be combined in whole or inpart.

The various methods or operations described herein may be implemented bya network element. An example network element is shown with regard toFIG. 25 . In FIG. 25 , network element 3110 includes a processor 3120and a communications subsystem 3130, where the processor 3120 andcommunications subsystem 3130 cooperate to perform the methods oroperations previously described.

Further, the various methods or operations described herein may beimplemented by a communications device (e.g., UEs, network nodes, TE,etc.). An example of a communications device is described below withregard to FIG. 26 . The communications device 3200 may comprise atwo-way wireless communication device having voice and datacommunication capabilities. In some embodiments, voice communicationcapabilities are optional. The communications device 3200 may have thecapability to communicate with other computer systems on the Internet.Depending on the exact functionality provided, the communications device3200 may be referred to as a data messaging device, a two-way pager, awireless e-mail device, a cellular telephone with data messagingcapabilities, a wireless Internet appliance, a wireless device, a smartphone, a mobile device, or a data communication device, as examples.

Where the communications device 3200 is enabled for two-waycommunication, it may incorporate a communication subsystem 3211,including a receiver 3212 and a transmitter 3214, as well as associatedcomponents such as one or more antenna elements 3216 and 3218, localoscillators (LOs) 3213, and a processing module such as a digital signalprocessor (DSP) 3220. The particular design of the communicationsubsystem 3211 may be dependent upon the communication network 3219 inwhich the communications device 3200 is intended to operate.

Network access may also vary depending upon the type of network 3219. Insome networks, network access is associated with a subscriber or user ofthe communications device 3200. The communications device 3200 may use aUSIM or eUICC in order to operate on a network. The USIM/eUICC interface3244 is typically similar to a card slot into which a USIM/eUICC cardmay be inserted. The USIM/eUICC card may have memory and may hold manykey configurations 3251 and other information 3253, such asidentification and subscriber-related information.

When network registration or activation procedures have been completed,the communications device 3200 may send and receive communicationsignals over the network 3219. As illustrated, the network 3219 maycomprise multiple base stations communicating with the communicationsdevice 3200.

Signals received by antenna 3216 through communication network 3219 areinput to receiver 3212, which may perform such common receiver functionsas signal amplification, frequency down conversion, filtering, channelselection, and the like. Analog to digital (A/D) conversion of areceived signal allows more complex communication functions, such asdemodulation and decoding to be performed in the DSP 3220. In a similarmanner, signals to be transmitted are processed, including modulationand encoding for example, by DSP 3220 and are input to transmitter 3214for digital to analog (D/A) conversion, frequency up conversion,filtering, amplification, and transmission over the communicationnetwork 3219 via antenna 3218. DSP 3220 not only processes communicationsignals but also provides for receiver and transmitter control. Forexample, the gains applied to communication signals in receiver 3212 andtransmitter 3214 may be adaptively controlled through automatic gaincontrol algorithms implemented in DSP 3220.

The communications device 3200 generally includes a processor 3238 whichcontrols the overall operation of the device. Communication functions,including data and voice communications, are performed throughcommunication subsystem 3211 in cooperation with the processor 3238.Processor 3238 also interacts with further device subsystems such as thedisplay 3222, flash memory 3224, random access memory (RAM) 3226,auxiliary input/output (I/O) subsystems 3228, serial port 3230, one ormore user interfaces such as keyboards or keypads 3232, speaker 3234,microphone 3236, one or more other communication subsystems 3240 such asa short-range communications subsystem, and any other device subsystemsgenerally designated as 3242. While the other communication subsystems3240 and device subsystems 3242 are depicted as separate components inFIG. 26 , it is to be understood that subsystems 3240 and devicesubsystems 3242 (or parts thereof) may be integrated as a singlecomponent. Serial port 3230 may include a USB port or other portcurrently known or developed in the future.

Some of the illustrated subsystems perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as keyboard 3232 and display3222, for example, may be used for both communication-related functions,such as entering a text message for transmission over a communicationnetwork, and device-resident functions, such as a calculator or tasklist.

Operating system software used by the processor 3238 may be stored in apersistent store such as flash memory 3224, which may instead be aread-only memory (ROM) or similar storage element (not shown). Theoperating system, specific device applications, or parts thereof, may betemporarily loaded into a volatile memory such as RAM 3226. Receivedcommunication signals may also be stored in RAM 3226.

As shown, flash memory 3224 may be constituted by different areas forboth computer programs 3258 and program data storage 3250, 3252, 3254,and 3256. These different storage types indicate that each program mayallocate a portion of flash memory 3224 for their own data storage use.Processor 3238, in addition to its operating system functions, mayenable execution of software applications on the communications device3200. A predetermined set of applications that control basic operations,including at least data and voice communication applications forexample, may typically be installed on the communications device 3200during manufacturing. Other applications may be installed subsequentlyor dynamically.

Applications and software may be stored on any computer-readable storagemedium. The computer-readable storage medium may be tangible or in atransitory/non-transitory medium such as optical (e.g., CD, DVD, etc.),magnetic (e.g., tape), or other memory currently known or developed inthe future.

Software applications may be loaded onto the communications device 3200through the network 3219, an auxiliary I/O subsystem 3228, serial port3230, short-range communications subsystem(s) 3240, or any othersuitable subsystem(s) 3242, and installed by a user in the RAM 3226 or anon-volatile store (not shown) for execution by the processor 3238. Suchflexibility in application installation may increase the functionalityof the communications device 3200 and may provide enhanced on-devicefunctions, communication-related functions, or both. For example, securecommunication applications may enable electronic commerce functions andother such financial transactions to be performed using thecommunications device 3200.

In a data communication mode, a received signal such as a text messageor web page download may be processed by the communication subsystem3211 and input to the processor 3238, which may further process thereceived signal for output to the display 3222, or alternatively to anauxiliary I/O device 3228.

For voice communications, overall operation of the communications device3200 is similar, except that received signals may typically be output toa speaker 3234 and signals for transmission may be generated by amicrophone 3236. Alternative voice or audio I/O subsystems, such as avoice message recording subsystem, may also be implemented on thecommunications device 3200. Although voice or audio signal output may beaccomplished primarily through the speaker 3234, display 3222 may alsobe used to provide an indication of the identity of a calling party, theduration of a voice call, or other voice call-related information, forexample.

Serial port 3230 may be implemented in a personal digital assistant(PDA)-type device for which synchronization with a user's desktopcomputer (not shown) may be desirable, but such a port is an optionaldevice component. Such a port 3230 may enable a user to set preferencesthrough an external device or software application and may extend thecapabilities of the communications device 3200 by providing forinformation or software downloads to the communications device 3200other than through a wireless communication network 3219. The alternatedownload path may, for example, be used to load an encryption key ontothe communications device 3200 through a direct and thus reliable andtrusted connection to thereby enable secure device communication. Serialport 3230 may further be used to connect the device to a computer to actas a modem.

Other communications subsystems 3240, such as a short-rangecommunications subsystem, are further optional components which mayprovide for communication between the communications device 3200 anddifferent systems or devices, which need not necessarily be similardevices. For example, one or more other subsystems 3240 may include aninfrared device and associated circuits and components or a Bluetooth™communication module to provide for communication with similarly enabledsystems and devices. Subsystems 3240 may further include non-cellularcommunications such as WI-FI, WiMAX, near field communication (NFC),BLUETOOTH, ProSe (Proximity Services) (e.g., sidelink, PC5, D2D, etc.)and/or radio frequency identification (RFID). The other communicationssubsystem(s) 3240 and/or device subsystem(s) 3242 may also be used tocommunicate with auxiliary devices such as tablet displays, keyboards orprojectors.

The communications device 3200 and other components described abovemight include a processing component that is capable of executinginstructions related to the actions described above. FIG. 27 illustratesan example of a system 3300 that includes a processing component 3310suitable for implementing one or more embodiments disclosed herein. Inaddition to the processor 3310 (which may be referred to as a centralprocessor unit or CPU), the system 3300 might include networkconnectivity devices 3320, random access memory (RAM) 3330, read onlymemory (ROM) 3340, secondary storage 3350, and input/output (I/O)devices 3360. These components might communicate with one another via abus 3370. In some cases, some of these components may not be present ormay be combined in various combinations with one another or with othercomponents not shown. These components might be located in a singlephysical entity or in more than one physical entity. Any actionsdescribed herein as being taken by the processor 3310 might be taken bythe processor 3310 alone or by the processor 3310 in conjunction withone or more components shown or not shown in the drawing, such as adigital signal processor (DSP) 3380. Although the DSP 3380 is shown as aseparate component, the DSP 3380 might be incorporated into theprocessor 3310.

The processor 3310 executes instructions, codes, computer programs, orscripts that it might access from the network connectivity devices 3320,RAM 3330, ROM 3340, or secondary storage 3350 (which might includevarious disk-based systems such as hard disk, floppy disk, or opticaldisk). While only one CPU 3310 is shown, multiple processors may bepresent. Thus, while instructions may be discussed as being executed bya processor, the instructions may be executed simultaneously, serially,or otherwise by one or multiple processors. The processor 3310 may beimplemented as one or more CPU chips.

The network connectivity devices 3320 may take the form of modems, modembanks, Ethernet devices, universal serial bus (USB) interface devices,serial interfaces, token ring devices, wireless local area network(WLAN) devices, radio transceiver devices such as code division multipleaccess (CDMA) devices, GSM radio transceiver devices, universal mobiletelecommunications system (UMTS) radio transceiver devices, LTE radiotransceiver devices, new generation radio transceiver devices, worldwideinteroperability for microwave access (WiMAX) devices, and/or otherwell-known devices for connecting to networks. These networkconnectivity devices 3320 may enable the processor 3310 to communicatewith the Internet or one or more telecommunications networks or othernetworks from which the processor 3310 might receive information or towhich the processor 3310 might output information. The networkconnectivity devices 3320 might also include one or more transceivercomponents 3325 capable of transmitting and/or receiving datawirelessly.

The RAM 3330 might be used to store volatile data and perhaps to storeinstructions that are executed by the processor 3310. The ROM 3340 is anon-volatile memory device that typically has a smaller memory capacitythan the memory capacity of the secondary storage 3350. ROM 3340 mightbe used to store instructions and perhaps data that are read duringexecution of the instructions. Access to both RAM 3330 and ROM 3340 istypically faster than to secondary storage 3350. The secondary storage3350 is typically comprised of one or more disk drives or tape drivesand might be used for non-volatile storage of data or as an over-flowdata storage device if RAM 3330 is not large enough to hold all workingdata. Secondary storage 3350 may be used to store programs that areloaded into RAM 3330 when such programs are selected for execution.

The I/O devices 3360 may include liquid crystal displays (LCDs), touchscreen displays, keyboards, keypads, switches, dials, mice, track balls,voice recognizers, card readers, paper tape readers, printers, videomonitors, or other well-known input/output devices. Also, thetransceiver 3325 might be considered to be a component of the I/Odevices 3360 instead of or in addition to being a component of thenetwork connectivity devices 3320.

In an embodiment, a method in a network node is provided. The method maycomprise receiving, by a network node from the UE, a first messagecomprising an active time request and a UE identifier of the UE;generating, by the network node, a second message comprising an activetime response determined based on whether mobile terminated (MT) data isawaiting transmission to the UE; and sending, by the network node, thesecond message.

In an embodiment, a method in a user equipment (UE) is provided. Themethod may comprise generating, by a UE, a first message comprising anactive time request and a UE identifier of the UE; sending, by the UE,the first message to a network node; receiving, by the UE, a secondmessage from the network node comprising an active time response;determining, by the UE, an active time value based upon the active timeresponse; setting, by the UE, an active time timer to the active timevalue; sending, by the UE, mobile originated (MO) traffic; and entering,by the UE, a power saving mode (PSM) after expiration of the active timetimer.

In an embodiment, a network node is provided. The network node maycomprise a memory; and a processor coupled to the memory. The processormay be configured to receive, from a user equipment (UE), a firstmessage comprising an active time request and a UE identifier of the UE;generate a second message comprising an active time response determinedbased on whether mobile terminated (MT) data is awaiting transmission tothe UE; and send the second message.

In an embodiment a user equipment (UE) is provided. The UE may comprisea memory; and a processor coupled to the memory. The processor may beconfigured to generate a first message comprising an active time requestand a UE identifier of the UE; send the first message to a network node;receive a second message from the network node comprising an active timeresponse; determine an active time value based upon the active timeresponse; set an active time timer to the active time value; send mobileoriginated (MO) traffic; and enter a power saving mode (PSM) afterexpiration of the active time timer.

The following are incorporated herein by reference for all purposes:3GPP TS23.682, 3GPP TS 23.301, 3GPP TS 24.008, 3GPP TS 27.007, 3GPP TS24.301, 3GPP TS 23.401, 3GPP TS 36.413, and 3GPP TS 36.331.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods may beembodied in many other specific forms without departing from the scopeof the present disclosure. The present examples are to be considered asillustrative and not restrictive, and the intention is not to be limitedto the details given herein. For example, the various elements orcomponents may be combined or integrated in another system or certainfeatures may be omitted, or not implemented.

Also, techniques, systems, subsystems and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as coupled or directly coupled orcommunicating with each other may be indirectly coupled or communicatingthrough some interface, device, or intermediate component, whetherelectrically, mechanically, or otherwise. Other examples of changes,substitutions, and alterations are ascertainable by one skilled in theart and could be made without departing from the spirit and scopedisclosed herein.

What is claimed is:
 1. A method in a user equipment (UE), the methodcomprising: generating, by a UE, a first message comprising an activetime request and a UE identifier of the UE; sending, by the UE, thefirst message to a network node; receiving, by the UE, a second messagefrom the network node comprising an active time response; determining,by the UE, an active time value based upon the active time response;setting, by the UE, an active time timer to the active time value;sending, by the UE, mobile originated (MO) traffic; and entering, by theUE, a power saving mode (PSM) after expiration of the active time timer,wherein the active time response comprises a mostly MO traffic (MMOT)support flag.
 2. The method of claim 1, wherein the active time requestcomprises a request to set the active time value to zero, and whereinthe active time response comprises the active time value set to zero. 3.The method of claim 1, wherein the active time request comprises arequest to set the active time value, wherein the active time responsecomprises a message waiting flag, and wherein the method furthercomprises: setting the active time value to zero when the messagewaiting flag is set to false; and setting the active time value to anactive time value included in the active time response when the messagewaiting flag is set to true.
 4. The method of claim 1, wherein themethod further comprises setting the active time value to zero for apredetermined time when the MMOT support flag is set to true, whereinthe predetermined time is stored at the UE or received from the networknode.
 5. The method of claim 1, wherein the active time requestcomprises an MMOT support flag.
 6. The method of claim 1, furthercomprising starting, by the UE, the active time timer when the UE beginssending the MO traffic.
 7. The method of claim 1, wherein the secondmessage comprises an S1 release comprising a PSM state transitionindicator, and wherein the method further comprises: setting the activetime value to zero when the PSM state transition indicator indicates aPSM deep sleep; and setting the active time value to an active timevalue included in the active time response when the PSM state transitionindicator indicates a PSM active time.
 8. The method of claim 1, furthercomprising starting, by the UE, the active time timer when the UEreceives a tracking area update accept message.
 9. The method of claim1, wherein the active time request comprises a session initiationpreference, wherein the session initiation preference comprises one ormore of a mobile session origination only preference or a MMOT trafficpreference.
 10. A user equipment (UE) comprising: a memory; and aprocessor coupled to the memory, the processor configured to: generate afirst message comprising an active time request and a UE identifier ofthe UE; send the first message to a network node; receive a secondmessage from the network node comprising an active time response;determine an active time value based upon the active time response; setan active time timer to the active time value; send mobile originated(MO) traffic; and enter a power saving mode (PSM) after expiration ofthe active time timer, wherein the active time response comprises amostly MO traffic (MMOT) support flag.
 11. The UE of claim 10, whereinthe active time request comprises a request to set the active time valueto zero, and wherein the active time response comprises the active timevalue set to zero.
 12. The UE of claim 10, wherein the active timerequest comprises a request to set the active time value, wherein theactive time response comprises a message waiting flag, and wherein theprocessor is further configured to: set the active time value to zerowhen the message waiting flag is set to false; and set the active timevalue to an active time value included in the active time response whenthe message waiting flag is set to true.
 13. The UE of claim 10, whereinthe processor is further configured to set the active time value to zerofor a predetermined time when the MMOT support flag is set to true,wherein the predetermined time is stored at the UE or received from thenetwork node.
 14. The UE of claim 10, wherein the active time requestcomprises an MMOT support flag.
 15. The UE of claim 10, wherein theprocessor is further configured to start the active time timer when theUE begins sending the MO traffic.
 16. The UE of claim 10, wherein thesecond message comprises an S1 release comprising a PSM state transitionindicator, and wherein the processor is further configured to: set theactive time value to zero when the PSM state transition indicatorindicates a PSM deep sleep; and set the active time value to an activetime value included in the active time response when the PSM statetransition indicator indicates a PSM active time.
 17. The UE of claim10, wherein the processor is further configured to start the active timetimer when the UE receives a tracking area update accept message. 18.The UE of claim 10, wherein the active time request comprises a sessioninitiation preference, wherein the session initiation preferencecomprises one or more of a mobile session origination only preference ora MMOT traffic preference.
 19. A non-transitory computer program productcomprising instructions which, when executed by a processor of a userequipment (UE), cause the UE to: generate a first message comprising anactive time request and a UE identifier of the UE; send the firstmessage to a network node; receive a second message from the networknode comprising an active time response; determine an active time valuebased upon the active time response; set an active time timer to theactive time value; send mobile originated (MO) traffic; and enter apower saving mode (PSM) after expiration of the active time timer,wherein the active time response comprises a mostly MO traffic (MMOT)support flag.
 20. The non-transitory computer program product of claim19, wherein the active time request comprises a request to set theactive time value to zero, and wherein the active time responsecomprises the active time value set to zero.